Device, method, and graphical user interface for managing user interface content and user interface elements

ABSTRACT

Alignment guides configured for velocity-sensitive behavior are disclosed. In one embodiment, during a user interface element move gesture, the gesture velocity is determined, and while moving the user interface element during the gesture, the user interface operates in a first or a second state with respect to displaying alignment guides. When the velocity of the user gesture exceeds a predefined velocity threshold, the display of the user interface is maintained in the first state, which does not include visibly displaying alignment guides. When the velocity of the user gesture is less than the predefined velocity threshold, the user interface is displayed in a second state that includes visibly displaying one or more alignment guides. In some embodiments, gesture velocity is used to set alignment guide attraction strength.

TECHNICAL FIELD

The disclosed embodiments relate generally to computing devices,including but not limited to, computing devices and methods for managinguser interface content and user interface elements.

BACKGROUND

The use of computers and other electronic computing devices to manageuser interface content and user interface elements has increasedsignificantly in recent years. Exemplary computing devices that includecapabilities of managing user interface content and user interfaceelements include mobile telephones, desktop computers, laptop computers,tablet computers, electronic book readers, consumer electronics,personal digital assistants, etc.

Many users rely on electronic computing devices for managing userinterface content and user interface elements. Unfortunately, existingmethods for managing user interface content and user interface elementsare cumbersome and inefficient. In addition, existing methods takelonger than necessary, thereby wasting energy. This latter considerationis particularly important in battery-operated devices.

Accordingly, there is a need for computing devices with faster, moreefficient methods and interfaces for managing user interface content anduser interface elements, such as using velocity sensitive alignmentguides during user interface element movement gestures. Such methods andinterfaces may complement or replace conventional methods for managinguser interface content and user interface elements. Such methods andinterfaces reduce the cognitive burden on a user and produce a moreefficient human-machine interface. For battery-operated computingdevices, such methods and interfaces conserve power and increase thetime between battery charges.

SUMMARY

The above deficiencies and other problems associated with userinterfaces for computing devices with touch-sensitive surfaces arereduced or eliminated by the disclosed devices. In some embodiments, thedevice is a desktop computer. In some embodiments, the device isportable (e.g., a notebook computer, tablet computer, or handhelddevice). In some embodiments, the device has a touchpad. In someembodiments, the device has a touch-sensitive display (also known as a“touch screen” or “touch screen display”). In some embodiments, thedevice has a graphical user interface (GUI), one or more processors,memory and one or more modules, programs or sets of instructions storedin the memory for performing multiple functions. In some embodiments,the user interacts with the GUI primarily through finger contacts andgestures on the touch-sensitive surface. In some embodiments, thefunctions may include image editing, drawing, presenting, wordprocessing, website creating, disk authoring, spreadsheet making, gameplaying, telephoning, video conferencing, e-mailing, instant messaging,workout support, digital photographing, digital video recording, webbrowsing, digital music playing, and/or digital video playing.Executable instructions for performing these functions may be includedin a computer readable storage medium or other computer program productconfigured for execution by one or more processors.

In accordance with some embodiments, a method is performed at acomputing device with a display and one or more user input devicesadapted to detect user gestures. The method includes displaying a userinterface in a first state, the user interface including at least: auser interface element configured to be moved within the user interfacein response to user gestures, and a plurality of alignment guidesadapted to indicate potential placement positions within the userinterface for user interface elements being moved; detecting a usergesture, the user gesture corresponding to a gesture to move the userinterface element within the user interface; determining a velocity ofthe user gesture; in response to detecting the user gesture, moving theuser interface element within the user interface in accordance with theuser gesture; while moving the user interface element within the userinterface: when the velocity of the user gesture is less than a firstpredefined velocity threshold, displaying the user interface in a secondstate, the second state including visibly displaying one or more of theplurality of alignment guides; and when the velocity of the user gestureexceeds the first predefined velocity threshold, maintaining display ofthe user interface in the first state.

In accordance with some embodiments, a computing device includes adisplay, one or more user input devices adapted to detect user gestures,one or more processors, memory, and one or more programs. The one ormore programs are stored in the memory and configured to be executed bythe one or more processors. The one or more programs includeinstructions for displaying a user interface in a first state, the userinterface including at least: a user interface element configured to bemoved within the user interface in response to user gestures, and aplurality of alignment guides adapted to indicate potential placementpositions within the user interface for user interface elements beingmoved; detecting a user gesture, the user gesture corresponding to agesture to move the user interface element within the user interface;determining a velocity of the user gesture; in response to detecting theuser gesture, moving the user interface element within the userinterface in accordance with the user gesture; while moving the userinterface element within the user interface: when the velocity of theuser gesture is less than a first predefined velocity threshold,displaying the user interface in a second state, the second stateincluding visibly displaying one or more of the plurality of alignmentguides; and when the velocity of the user gesture exceeds the firstpredefined velocity threshold, maintaining display of the user interfacein the first state.

In accordance with some embodiments there is a graphical user interfaceon a computing device with a display, one or more user input devicesadapted to detect user gestures, a memory, and one or more processors toexecute one or more programs stored in the memory. The graphical userinterface includes a user interface including at least a user interfaceelement configured to be moved within the user interface in response touser gestures, and a plurality of alignment guides adapted to indicatepotential placement positions within the user interface for userinterface elements being moved; wherein, while the user interface is ina first state: a user gesture is detected, the user gesturecorresponding to a gesture to move the user interface element within theuser interface; a velocity of the user gesture is determined; inresponse to detecting the user gesture, the user interface element ismoved within the user interface in accordance with the user gesture;while moving the user interface element within the user interface: whenthe velocity of the user gesture is less than a first predefinedvelocity threshold, the user interface is displayed in a second state,the second state including visibly displaying one or more of theplurality of alignment guides; and when the velocity of the user gestureexceeds the first predefined velocity threshold, display of the userinterface in the first state is maintained.

In accordance with some embodiments, a computer readable storage mediumhas stored therein one or more programs, the one or more programscomprising instructions, which when executed by a computing device witha display and one or more user input devices adapted to detect usergestures, cause the computing device to display a user interface in afirst state, the user interface including at least: a user interfaceelement configured to be moved within the user interface in response touser gestures, and a plurality of alignment guides adapted to indicatepotential placement positions within the user interface for userinterface elements being moved; detect a user gesture, the user gesturecorresponding to a gesture to move the user interface element within theuser interface; determine a velocity of the user gesture; in response todetecting the user gesture, move the user interface element within theuser interface in accordance with the user gesture; while moving theuser interface element within the user interface: when the velocity ofthe user gesture is less than a first predefined velocity threshold,display the user interface in a second state, the second state includingvisibly displaying one or more of the plurality of alignment guides; andwhen the velocity of the user gesture exceeds the first predefinedvelocity threshold, maintain display of the user interface in the firststate.

In accordance with some embodiments, a computing device includes adisplay; one or more user input devices adapted to detect user gestures;and means for displaying a user interface in a first state, the userinterface including at least: a user interface element configured to bemoved within the user interface in response to user gestures, and aplurality of alignment guides adapted to indicate potential placementpositions within the user interface for user interface elements beingmoved; means for detecting a user gesture, the user gesturecorresponding to a gesture to move the user interface element within theuser interface; means for determining a velocity of the user gesture; inresponse to detecting the user gesture, means for moving the userinterface element within the user interface in accordance with the usergesture; while moving the user interface element within the userinterface: when the velocity of the user gesture is less than a firstpredefined velocity threshold, means for displaying the user interfacein a second state, the second state including visibly displaying one ormore of the plurality of alignment guides; and when the velocity of theuser gesture exceeds the first predefined velocity threshold, means formaintaining display of the user interface in the first state.

In accordance with some embodiments, an information processing apparatusfor use in a computing device includes a display, one or more user inputdevices adapted to detect user gestures, and means for displaying a userinterface in a first state, the user interface including at least: auser interface element configured to be moved within the user interfacein response to user gestures, and a plurality of alignment guidesadapted to indicate potential placement positions within the userinterface for user interface elements being moved; means for detecting auser gesture, the user gesture corresponding to a gesture to move theuser interface element within the user interface; means for determininga velocity of the user gesture; in response to detecting the usergesture, means for moving the user interface element within the userinterface in accordance with the user gesture; while moving the userinterface element within the user interface: when the velocity of theuser gesture is less than a first predefined velocity threshold, meansfor displaying the user interface in a second state, the second stateincluding visibly displaying one or more of the plurality of alignmentguides; and when the velocity of the user gesture exceeds the firstpredefined velocity threshold, means for maintaining display of the userinterface in the first state.

In accordance with some embodiments, a method is performed at acomputing device with a display and one or more user input devicesadapted to detect user gestures. The method includes: displaying a userinterface including at least: a user interface element configured to bemoved within the user interface in response to user gestures, and aplurality of alignment guides adapted to indicate potential placementpositions within the user interface for user interface elements beingmoved, wherein one or more of the plurality of alignment guides areconfigured with a first attraction strength; detecting a user gesture,the user gesture corresponding to a gesture to move the user interfaceelement within the user interface; determining a velocity of the usergesture; in response to detecting the user gesture, moving the userinterface element within the user interface in accordance with the usergesture; while moving the user interface element within the userinterface: when the velocity of the user gesture is less than apredefined velocity threshold, maintaining the first attractionstrength; and when the velocity of the user gesture exceeds thepredefined velocity threshold, configuring one or more of the pluralityof alignment guides with a second attraction strength.

In accordance with some embodiments, a computing device includes adisplay, one or more user input devices adapted to detect user gestures,one or more processors, memory, and one or more programs. The one ormore programs are stored in the memory and configured to be executed bythe one or more processors. The one or more programs includeinstructions for displaying a user interface including at least: a userinterface element configured to be moved within the user interface inresponse to user gestures, and a plurality of alignment guides adaptedto indicate potential placement positions within the user interface foruser interface elements being moved, wherein one or more of theplurality of alignment guides are configured with a first attractionstrength; detecting a user gesture, the user gesture corresponding to agesture to move the user interface element within the user interface;determining a velocity of the user gesture; in response to detecting theuser gesture, moving the user interface element within the userinterface in accordance with the user gesture; while moving the userinterface element within the user interface: when the velocity of theuser gesture is less than a predefined velocity threshold, maintainingthe first attraction strength; and when the velocity of the user gestureexceeds the predefined velocity threshold, configuring one or more ofthe plurality of alignment guides with a second attraction strength.

In accordance with some embodiments there is a graphical user interfaceon a computing device with a display, one or more user input devicesadapted to detect user gestures, a memory, and one or more processors toexecute one or more programs stored in the memory. The graphical userinterface includes a user interface including at least: a user interfaceelement configured to be moved within the user interface in response touser gestures, and a plurality of alignment guides adapted to indicatepotential placement positions within the user interface for userinterface elements being moved, wherein one or more of the plurality ofalignment guides are configured with a first attraction strength;wherein: a user gesture is detected, the user gesture corresponding to agesture to move the user interface element within the user interface; avelocity of the user gesture is determined; in response to detecting theuser gesture, the user interface element is moved within the userinterface in accordance with the user gesture; while moving the userinterface element within the user interface: when the velocity of theuser gesture is less than a predefined velocity threshold, the firstattraction strength is maintained; and when the velocity of the usergesture exceeds the predefined velocity threshold, one or more of theplurality of alignment guides are configured with a second attractionstrength.

In accordance with some embodiments, a computer readable storage mediumhas stored therein one or more programs, the one or more programscomprising instructions, which when executed by a computing device witha display and one or more user input devices adapted to detect usergestures, cause the computing device to display a user interfaceincluding at least: a user interface element configured to be movedwithin the user interface in response to user gestures, and a pluralityof alignment guides adapted to indicate potential placement positionswithin the user interface for user interface elements being moved,wherein one or more of the plurality of alignment guides are configuredwith a first attraction strength; detect a user gesture, the usergesture corresponding to a gesture to move the user interface elementwithin the user interface; determine a velocity of the user gesture; inresponse to detecting the user gesture, move the user interface elementwithin the user interface in accordance with the user gesture; whilemoving the user interface element within the user interface: when thevelocity of the user gesture is less than a predefined velocitythreshold, maintain the first attraction strength; and when the velocityof the user gesture exceeds the predefined velocity threshold, configureone or more of the plurality of alignment guides with a secondattraction strength.

In accordance with some embodiments, a computing device includes adisplay; one or more user input devices adapted to detect user gestures;and means for displaying a user interface including at least: a userinterface element configured to be moved within the user interface inresponse to user gestures, and a plurality of alignment guides adaptedto indicate potential placement positions within the user interface foruser interface elements being moved, wherein one or more of theplurality of alignment guides are configured with a first attractionstrength; means for detecting a user gesture, the user gesturecorresponding to a gesture to move the user interface element within theuser interface; means for determining a velocity of the user gesture; inresponse to detecting the user gesture, means for moving the userinterface element within the user interface in accordance with the usergesture; while moving the user interface element within the userinterface: when the velocity of the user gesture is less than apredefined velocity threshold, means for maintaining the firstattraction strength; and when the velocity of the user gesture exceedsthe predefined velocity threshold, means for configuring one or more ofthe plurality of alignment guides with a second attraction strength.

In accordance with some embodiments, an information processing apparatusfor use in a computing device includes a display, one or more user inputdevices adapted to detect user gestures, and means for displaying a userinterface including at least: a user interface element configured to bemoved within the user interface in response to user gestures, and aplurality of alignment guides adapted to indicate potential placementpositions within the user interface for user interface elements beingmoved, wherein one or more of the plurality of alignment guides areconfigured with a first attraction strength; means for detecting a usergesture, the user gesture corresponding to a gesture to move the userinterface element within the user interface; means for determining avelocity of the user gesture; in response to detecting the user gesture,means for moving the user interface element within the user interface inaccordance with the user gesture; while moving the user interfaceelement within the user interface: when the velocity of the user gestureis less than a predefined velocity threshold, means for maintaining thefirst attraction strength; and when the velocity of the user gestureexceeds the predefined velocity threshold, means for configuring one ormore of the plurality of alignment guides with a second attractionstrength.

Thus, the computing devices disclosed herein are provided with faster,more efficient methods and interfaces for managing user interfacecontent and user interface elements, including use of velocity sensitivealignment guides during user interface element movement and resizegestures. These computing devices with faster, more efficient methodsand interfaces increase user effectiveness, efficiency, andsatisfaction. Such methods and interfaces may complement or replaceconventional methods for manipulating user interface objects.

BRIEF DESCRIPTION OF THE DRAWINGS

For a better understanding of the aforementioned embodiments of theinvention as well as additional embodiments thereof, reference should bemade to the Description of Embodiments below, in conjunction with thefollowing drawings in which like reference numerals refer tocorresponding parts throughout the figures.

FIGS. 1A and 1B are block diagrams illustrating portable multifunctiondevices with touch-sensitive displays in accordance with someembodiments.

FIG. 1C is a block diagram illustrating exemplary components for eventhandling in accordance with some embodiments.

FIG. 2 illustrates a portable multifunction device having a touch screenin accordance with some embodiments.

FIG. 3 is a block diagram of an exemplary multifunction device with adisplay and a touch-sensitive surface in accordance with someembodiments.

FIGS. 4A and 4B illustrate exemplary user interfaces for a menu ofapplications on a portable multifunction device in accordance with someembodiments.

FIG. 4C illustrates an exemplary user interface for a multifunctiondevice with a touch-sensitive surface that is separate from the displayin accordance with some embodiments.

FIGS. 5A-5M illustrate exemplary user interfaces for manipulating userinterface objects in accordance with some embodiments.

FIGS. 6A-6C are flow diagrams illustrating a method of manipulating userinterface objects in accordance with some embodiments.

DESCRIPTION OF EMBODIMENTS

Reference will now be made in detail to embodiments, examples of whichare illustrated in the accompanying drawings. In the following detaileddescription, numerous specific details are set forth in order to providea thorough understanding of the present invention. However, it will beapparent to one of ordinary skill in the art that the present inventionmay be practiced without these specific details. In other instances,well-known methods, procedures, components, circuits, and networks havenot been described in detail so as not to unnecessarily obscure aspectsof the embodiments.

It will also be understood that, although the terms first, second, etc.may be used herein to describe various elements, these elements shouldnot be limited by these terms. These terms are only used to distinguishone element from another. For example, a first contact could be termed asecond contact, and, similarly, a second contact could be termed a firstcontact, without departing from the scope of the present invention. Thefirst contact and the second contact are both contacts, but they are notthe same contact.

The terminology used in the description of the invention herein is forthe purpose of describing particular embodiments only and is notintended to be limiting of the invention. As used in the description ofthe invention and the appended claims, the singular forms “a”, “an” and“the” are intended to include the plural forms as well, unless thecontext clearly indicates otherwise. It will also be understood that theterm “and/or” as used herein refers to and encompasses any and allpossible combinations of one or more of the associated listed items. Itwill be further understood that the terms “includes,” “including,”“comprises,” and/or “comprising,” when used in this specification,specify the presence of stated features, integers, steps, operations,elements, and/or components, but do not preclude the presence oraddition of one or more other features, integers, steps, operations,elements, components, and/or groups thereof.

As used herein, the term “if” may be construed to mean “when” or “upon”or “in response to determining” or “in response to detecting,” dependingon the context. Similarly, the phrase “if it is determined” or “if [astated condition or event] is detected” may be construed to mean “upondetermining” or “in response to determining” or “upon detecting [thestated condition or event]” or “in response to detecting [the statedcondition or event],” depending on the context.

As used herein, the term “resolution” of a display refers to the numberof pixels (also called “pixel counts” or “pixel resolution”) along eachaxis or in each dimension of the display. For example, a display mayhave a resolution of 320×480 pixels. Furthermore, as used herein, theterm “resolution” of a multifunction device refers to the resolution ofa display in the multifunction device. The term “resolution” does notimply any limitations on the size of each pixel or the spacing ofpixels. For example, compared to a first display with a 1024×768-pixelresolution, a second display with a 320×480-pixel resolution has a lowerresolution. However, it should be noted that the physical size of adisplay depends not only on the pixel resolution, but also on many otherfactors, including the pixel size and the spacing of pixels. Therefore,the first display may have the same, smaller, or larger physical size,compared to the second display.

As used herein, the term “video resolution” of a display refers to thedensity of pixels along each axis or in each dimension of the display.The video resolution is often measured in a dots-per-inch (DPI) unit,which counts the number of pixels that can be placed in a line withinthe span of one inch along a respective dimension of the display.

Embodiments of computing devices, user interfaces for such devices, andassociated processes for using such devices are described. In someembodiments, the computing device is a portable communications device,such as a mobile telephone, that also contains other functions, such asPDA and/or music player functions. Exemplary embodiments of portablemultifunction devices include, without limitation, the iPhone® and iPodTouch® devices from Apple Inc. of Cupertino, Calif. Other portabledevices, such as laptops or tablet computers with touch-sensitivesurfaces (e.g., touch screen displays and/or touch pads), may also beused. It should also be understood that, in some embodiments, the deviceis not a portable communications device, but is a desktop computer witha touch-sensitive surface (e.g., a touch screen display and/or a touchpad).

In the discussion that follows, a computing device that includes adisplay and a touch-sensitive surface is described. It should beunderstood, however, that the computing device may include one or moreother physical user-interface devices, such as a physical keyboard, amouse and/or a joystick.

The device supports a variety of applications, such as one or more ofthe following: a drawing application, a presentation application, a wordprocessing application, a website creation application, a disk authoringapplication, a spreadsheet application, a gaming application, atelephone application, a video conferencing application, an e-mailapplication, an instant messaging application, a workout supportapplication, a photo management application, a digital cameraapplication, a digital video camera application, a web browsingapplication, a digital music player application, and/or a digital videoplayer application.

The various applications that may be executed on the device may use atleast one common physical user-interface device, such as thetouch-sensitive surface. One or more functions of the touch-sensitivesurface as well as corresponding information displayed on the device maybe adjusted and/or varied from one application to the next and/or withina respective application. In this way, a common physical architecture(such as the touch-sensitive surface) of the device may support thevariety of applications with user interfaces that are intuitive andtransparent to the user.

The user interfaces may include one or more soft keyboard embodiments.The soft keyboard embodiments may include standard (QWERTY) and/ornon-standard configurations of symbols on the displayed icons of thekeyboard, such as those described in U.S. patent application Ser. Nos.11/459,606, “Keyboards For Portable Electronic Devices,” filed Jul. 24,2006, and 11/459,615, “Touch Screen Keyboards For Portable ElectronicDevices,” filed Jul. 24, 2006, the contents of which are herebyincorporated by reference in their entireties. The keyboard embodimentsmay include a reduced number of icons (or soft keys) relative to thenumber of keys in existing physical keyboards, such as that for atypewriter. This may make it easier for users to select one or moreicons in the keyboard, and thus, one or more corresponding symbols. Thekeyboard embodiments may be adaptive. For example, displayed icons maybe modified in accordance with user actions, such as selecting one ormore icons and/or one or more corresponding symbols. One or moreapplications on the device may utilize common and/or different keyboardembodiments. Thus, the keyboard embodiment used may be tailored to atleast some of the applications. In some embodiments, one or morekeyboard embodiments may be tailored to a respective user. For example,one or more keyboard embodiments may be tailored to a respective userbased on a word usage history (lexicography, slang, individual usage) ofthe respective user. Some of the keyboard embodiments may be adjusted toreduce a probability of a user error when selecting one or more icons,and thus one or more symbols, when using the soft keyboard embodiments.

Attention is now directed toward embodiments of portable devices withtouch-sensitive displays. FIGS. 1A and 1B are block diagramsillustrating portable multifunction devices 100 with touch-sensitivedisplays 112 in accordance with some embodiments. Touch-sensitivedisplay 112 is sometimes called a “touch screen” for convenience, andmay also be known as or called a touch-sensitive display system. Device100 may include memory 102 (which may include one or more computerreadable storage mediums), memory controller 122, one or more processingunits (CPU's) 120, peripherals interface 118, RF circuitry 108, audiocircuitry 110, speaker 111, microphone 113, input/output (I/O) subsystem106, other input or control devices 116, and external port 124. Device100 may include one or more optical sensors 164. These components maycommunicate over one or more communication buses or signal lines 103.

It should be appreciated that device 100 is only one example of aportable multifunction device, and that device 100 may have more orfewer components than shown, may combine two or more components, or mayhave a different configuration or arrangement of the components. Thevarious components shown in FIGS. 1A and 1B may be implemented inhardware, software, or a combination of both hardware and software,including one or more signal processing and/or application specificintegrated circuits.

Memory 102 may include high-speed random access memory and may alsoinclude non-volatile memory, such as one or more magnetic disk storagedevices, flash memory devices, or other non-volatile solid-state memorydevices. Access to memory 102 by other components of device 100, such asCPU 120 and the peripherals interface 118, may be controlled by memorycontroller 122.

Peripherals interface 118 can be used to couple input and outputperipherals of the device to CPU 120 and memory 102. The one or moreprocessors 120 run or execute various software programs and/or sets ofinstructions stored in memory 102 to perform various functions fordevice 100 and to process data.

In some embodiments, peripherals interface 118, CPU 120, and memorycontroller 122 may be implemented on a single chip, such as chip 104. Insome other embodiments, they may be implemented on separate chips.

RF (radio frequency) circuitry 108 receives and sends RF signals, alsocalled electromagnetic signals. RF circuitry 108 converts electricalsignals to/from electromagnetic signals and communicates withcommunications networks and other communications devices via theelectromagnetic signals. RF circuitry 108 may include well-knowncircuitry for performing these functions, including but not limited toan antenna system, an RF transceiver, one or more amplifiers, a tuner,one or more oscillators, a digital signal processor, a CODEC chipset, asubscriber identity module (SIM) card, memory, and so forth. RFcircuitry 108 may communicate with networks, such as the Internet, alsoreferred to as the World Wide Web (WWW), an intranet and/or a wirelessnetwork, such as a cellular telephone network, a wireless local areanetwork (LAN) and/or a metropolitan area network (MAN), and otherdevices by wireless communication. The wireless communication may useany of a plurality of communications standards, protocols andtechnologies, including but not limited to Global System for MobileCommunications (GSM), Enhanced Data GSM Environment (EDGE), high-speeddownlink packet access (HSDPA), wideband code division multiple access(W-CDMA), code division multiple access (CDMA), time division multipleaccess (TDMA), Bluetooth, Wireless Fidelity (Wi-Fi) (e.g., IEEE 802.11a,IEEE 802.11b, IEEE 802.11g and/or IEEE 802.11n), voice over InternetProtocol (VoIP), Wi-MAX, a protocol for e-mail (e.g., Internet messageaccess protocol (IMAP) and/or post office protocol (POP)), instantmessaging (e.g., extensible messaging and presence protocol (XMPP),Session Initiation Protocol for Instant Messaging and PresenceLeveraging Extensions (SIMPLE), Instant Messaging and Presence Service(IMPS)), and/or Short Message Service (SMS), or any other suitablecommunication protocol, including communication protocols not yetdeveloped as of the filing date of this document.

Audio circuitry 110, speaker 111, and microphone 113 provide an audiointerface between a user and device 100. Audio circuitry 110 receivesaudio data from peripherals interface 118, converts the audio data to anelectrical signal, and transmits the electrical signal to speaker 111.Speaker 111 converts the electrical signal to human-audible sound waves.Audio circuitry 110 also receives electrical signals converted bymicrophone 113 from sound waves. Audio circuitry 110 converts theelectrical signal to audio data and transmits the audio data toperipherals interface 118 for processing. Audio data may be retrievedfrom and/or transmitted to memory 102 and/or RF circuitry 108 byperipherals interface 118. In some embodiments, audio circuitry 110 alsoincludes a headset jack (e.g., 212, FIG. 2). The headset jack providesan interface between audio circuitry 110 and removable audioinput/output peripherals, such as output-only headphones or a headsetwith both output (e.g., a headphone for one or both ears) and input(e.g., a microphone).

I/O subsystem 106 couples input/output peripherals on device 100, suchas touch screen 112 and other input control devices 116, to peripheralsinterface 118. I/O subsystem 106 may include display controller 156 andone or more input controllers 160 for other input or control devices.The one or more input controllers 160 receive/send electrical signalsfrom/to other input or control devices 116. The other input controldevices 116 may include physical buttons (e.g., push buttons, rockerbuttons, etc.), dials, slider switches, joysticks, click wheels, and soforth. In some alternate embodiments, input controller(s) 160 may becoupled to any (or none) of the following: a keyboard, infrared port,USB port, and a pointer device such as a mouse. The one or more buttons(e.g., 208, FIG. 2) may include an up/down button for volume control ofspeaker 111 and/or microphone 113. The one or more buttons may include apush button (e.g., 206, FIG. 2). A quick press of the push button maydisengage a lock of touch screen 112 or begin a process that usesgestures on the touch screen to unlock the device, as described in U.S.patent application Ser. No. 11/322,549, “Unlocking a Device byPerforming Gestures on an Unlock Image,” filed Dec. 23, 2005, which ishereby incorporated by reference in its entirety. A longer press of thepush button (e.g., 206) may turn power to device 100 on or off. The usermay be able to customize a functionality of one or more of the buttons.Touch screen 112 is used to implement virtual or soft buttons and one ormore soft keyboards.

Touch-sensitive display 112 provides an input interface and an outputinterface between the device and a user. Display controller 156 receivesand/or sends electrical signals from/to touch screen 112. Touch screen112 displays visual output to the user. The visual output may includegraphics, text, icons, video, and any combination thereof (collectivelytermed “graphics”). In some embodiments, some or all of the visualoutput may correspond to user-interface objects.

Touch screen 112 has a touch-sensitive surface, sensor or set of sensorsthat accepts input from the user based on haptic and/or tactile contact.Touch screen 112 and display controller 156 (along with any associatedmodules and/or sets of instructions in memory 102) detect contact (andany movement or breaking of the contact) on touch screen 112 andconverts the detected contact into interaction with user-interfaceobjects (e.g., one or more soft keys, icons, web pages or images) thatare displayed on touch screen 112. In an exemplary embodiment, a pointof contact between touch screen 112 and the user corresponds to a fingerof the user.

Touch screen 112 may use LCD (liquid crystal display) technology, LPD(light emitting polymer display) technology, or LED (light emittingdiode) technology, although other display technologies may be used inother embodiments. Touch screen 112 and display controller 156 maydetect contact and any movement or breaking thereof using any of aplurality of touch sensing technologies now known or later developed,including but not limited to capacitive, resistive, infrared, andsurface acoustic wave technologies, as well as other proximity sensorarrays or other elements for determining one or more points of contactwith touch screen 112. In an exemplary embodiment, projected mutualcapacitance sensing technology is used, such as that found in theiPhone® and iPod Touch® from Apple Inc. of Cupertino, Calif.

A touch-sensitive display in some embodiments of touch screen 112 may beanalogous to the multi-touch sensitive touchpads described in thefollowing U.S. Pat. Nos. 6,323,846 (Westerman et al.), 6,570,557(Westerman et al.), and/or 6,677,932 (Westerman), and/or U.S. PatentPublication 2002/0015024A1, each of which is hereby incorporated byreference in its entirety. However, touch screen 112 displays visualoutput from portable device 100, whereas touch sensitive touchpads donot provide visual output.

A touch-sensitive display in some embodiments of touch screen 112 may beas described in the following applications: (1) U.S. patent applicationSer. No. 11/381,313, “Multipoint Touch Surface Controller,” filed May 2,2006; (2) U.S. patent application Ser. No. 10/840,862, “MultipointTouchscreen,” filed May 6, 2004; (3) U.S. patent application Ser. No.10/903,964, “Gestures For Touch Sensitive Input Devices,” filed Jul. 30,2004; (4) U.S. patent application Ser. No. 11/048,264, “Gestures ForTouch Sensitive Input Devices,” filed Jan. 31, 2005; (5) U.S. patentapplication Ser. No. 11/038,590, “Mode-Based Graphical User InterfacesFor Touch Sensitive Input Devices,” filed Jan. 18, 2005; (6) U.S. patentapplication Ser. No. 11/228,758, “Virtual Input Device Placement On ATouch Screen User Interface,” filed Sep. 16, 2005; (7) U.S. patentapplication Ser. No. 11/228,700, “Operation Of A Computer With A TouchScreen Interface,” filed Sep. 16, 2005; (8) U.S. patent application Ser.No. 11/228,737, “Activating Virtual Keys Of A Touch-Screen VirtualKeyboard,” filed Sep. 16, 2005; and (9) U.S. patent application Ser. No.11/367,749, “Multi-Functional Hand-Held Device,” filed Mar. 3, 2006. Allof these applications are incorporated by reference herein in theirentirety.

Touch screen 112 may have a video resolution in excess of 100 dpi. Insome embodiments, the touch screen has a video resolution ofapproximately 160 dpi. The user may make contact with touch screen 112using any suitable object or appendage, such as a stylus, a finger, andso forth. In some embodiments, the user interface is designed to workprimarily with finger-based contacts and gestures, which can be lessprecise than stylus-based input due to the larger area of contact of afinger on the touch screen. In some embodiments, the device translatesthe rough finger-based input into a precise pointer/cursor position orcommand for performing the actions desired by the user.

In some embodiments, in addition to the touch screen, device 100 mayinclude a touchpad (not shown) for activating or deactivating particularfunctions. In some embodiments, the touchpad is a touch-sensitive areaof the device that, unlike the touch screen, does not display visualoutput. The touchpad may be a touch-sensitive surface that is separatefrom touch screen 112 or an extension of the touch-sensitive surfaceformed by the touch screen.

In some embodiments, device 100 may include a physical or virtual wheel(e.g., a click wheel) as input control device 116. A user may navigateamong and interact with one or more graphical objects (e.g., icons)displayed in touch screen 112 by rotating the click wheel or by moving apoint of contact with the click wheel (e.g., where the amount ofmovement of the point of contact is measured by its angular displacementwith respect to a center point of the click wheel). The click wheel mayalso be used to select one or more of the displayed icons. For example,the user may press down on at least a portion of the click wheel or anassociated button. User commands and navigation commands provided by theuser via the click wheel may be processed by input controller 160 aswell as one or more of the modules and/or sets of instructions in memory102. For a virtual click wheel, the click wheel and click wheelcontroller may be part of touch screen 112 and display controller 156,respectively. For a virtual click wheel, the click wheel may be eitheran opaque or semitransparent object that appears and disappears on thetouch screen display in response to user interaction with the device. Insome embodiments, a virtual click wheel is displayed on the touch screenof a portable multifunction device and operated by user contact with thetouch screen.

Device 100 also includes power system 162 for powering the variouscomponents. Power system 162 may include a power management system, oneor more power sources (e.g., battery, alternating current (AC)), arecharging system, a power failure detection circuit, a power converteror inverter, a power status indicator (e.g., a light-emitting diode(LED)) and any other components associated with the generation,management and distribution of power in portable devices.

Device 100 may also include one or more optical sensors 164. FIGS. 1Aand 1B show an optical sensor coupled to optical sensor controller 158in I/O subsystem 106. Optical sensor 164 may include a charge-coupleddevice (CCD) or complementary metal-oxide semiconductor (CMOS)phototransistors. Optical sensor 164 receives light from theenvironment, projected through one or more lens, and converts the lightto data representing an image. In conjunction with imaging module 143(also called a camera module), optical sensor 164 may capture stillimages or video. In some embodiments, an optical sensor is located onthe back of device 100, opposite touch screen display 112 on the frontof the device, so that the touch screen display may be used as aviewfinder for still and/or video image acquisition. In someembodiments, an optical sensor is located on the front of the device sothat the user's image may be obtained for videoconferencing while theuser views the other video conference participants on the touch screendisplay. In some embodiments, the position of optical sensor 164 can bechanged by the user (e.g., by rotating the lens and the sensor in thedevice housing) so that a single optical sensor 164 may be used alongwith the touch screen display for both video conferencing and stilland/or video image acquisition.

Device 100 may also include one or more proximity sensors 166. FIGS. 1Aand 1B show proximity sensor 166 coupled to peripherals interface 118.Alternately, proximity sensor 166 may be coupled to input controller 160in I/O subsystem 106. Proximity sensor 166 may perform as described inU.S. patent application Ser. Nos. 11/241,839, “Proximity Detector InHandheld Device”; 11/240,788, “Proximity Detector In Handheld Device”;11/620,702, “Using Ambient Light Sensor To Augment Proximity SensorOutput”; 11/586,862, “Automated Response To And Sensing Of User ActivityIn Portable Devices”; and 11/638,251, “Methods And Systems For AutomaticConfiguration Of Peripherals,” which are hereby incorporated byreference in their entirety. In some embodiments, the proximity sensorturns off and disables touch screen 112 when the multifunction device isplaced near the user's ear (e.g., when the user is making a phone call).

Device 100 may also include one or more accelerometers 168. FIGS. 1A and1B show accelerometer 168 coupled to peripherals interface 118.Alternately, accelerometer 168 may be coupled to an input controller 160in I/O subsystem 106. Accelerometer 168 may perform as described in U.S.Patent Publication No. 2005/0190059, “Acceleration-based Theft DetectionSystem for Portable Electronic Devices,” and U.S. Patent Publication No.2006/0017692, “Methods And Apparatuses For Operating A Portable DeviceBased On An Accelerometer,” both of which are which are incorporated byreference herein in their entirety. In some embodiments, information isdisplayed on the touch screen display in a portrait view or a landscapeview based on an analysis of data received from the one or moreaccelerometers. Device 100 optionally includes, in addition toaccelerometer(s) 168, a magnetometer (not shown) and a GPS (or GLONASSor other global navigation system) receiver (not shown) for obtaininginformation concerning the location and orientation (e.g., portrait orlandscape) of device 100.

In some embodiments, the software components stored in memory 102include operating system 126, communication module (or set ofinstructions) 128, contact/motion module (or set of instructions) 130,graphics module (or set of instructions) 132, text input module (or setof instructions) 134, Global Positioning System (GPS) module (or set ofinstructions) 135, and applications (or sets of instructions) 136.Furthermore, in some embodiments memory 102 stores device/globalinternal state 157, as shown in FIGS. 1A, 1B and 3. Device/globalinternal state 157 includes one or more of: active application state,indicating which applications, if any, are currently active; displaystate, indicating what applications, views or other information occupyvarious regions of touch screen display 112; sensor state, includinginformation obtained from the device's various sensors and input controldevices 116; and location information concerning the device's locationand/or attitude.

Operating system 126 (e.g., Darwin, RTXC, LINUX, UNIX, OS X, WINDOWS, oran embedded operating system such as VxWorks) includes various softwarecomponents and/or drivers for controlling and managing general systemtasks (e.g., memory management, storage device control, powermanagement, etc.) and facilitates communication between various hardwareand software components.

Communication module 128 facilitates communication with other devicesover one or more external ports 124 and also includes various softwarecomponents for handling data received by RF circuitry 108 and/orexternal port 124. External port 124 (e.g., Universal Serial Bus (USB),FIREWIRE, etc.) is adapted for coupling directly to other devices orindirectly over a network (e.g., the Internet, wireless LAN, etc.). Insome embodiments, the external port is a multi-pin (e.g., 30-pin)connector that is the same as, or similar to and/or compatible with the30-pin connector used on iPod (trademark of Apple Inc.) devices.

Contact/motion module 130 may detect contact with touch screen 112 (inconjunction with display controller 156) and other touch sensitivedevices (e.g., a touchpad or physical click wheel). Contact/motionmodule 130 includes various software components for performing variousoperations related to detection of contact, such as determining ifcontact has occurred (e.g., detecting a finger-down event), determiningif there is movement of the contact and tracking the movement across thetouch-sensitive surface (e.g., detecting one or more finger-draggingevents), and determining if the contact has ceased (e.g., detecting afinger-up event or a break in contact). Contact/motion module 130receives contact data from the touch-sensitive surface. Determiningmovement of the point of contact, which is represented by a series ofcontact data, may include determining speed (magnitude), velocity(magnitude and direction), and/or an acceleration (a change in magnitudeand/or direction) of the point of contact. These operations may beapplied to single contacts (e.g., one finger contacts) or to multiplesimultaneous contacts (e.g., “multitouch”/multiple finger contacts). Insome embodiments, contact/motion module 130 and display controller 156detects contact on a touchpad. In some embodiments, contact/motionmodule 130 and controller 160 detects contact on a click wheel.

Contact/motion module 130 may detect a gesture input by a user.Different gestures on the touch-sensitive surface have different contactpatterns. Thus, a gesture may be detected by detecting a particularcontact pattern. For example, detecting a finger tap gesture includesdetecting a finger-down event followed by detecting a finger-up (liftoff) event at the same position (or substantially the same position) asthe finger-down event (e.g., at the position of an icon). As anotherexample, detecting a finger swipe gesture on the touch-sensitive surfaceincludes detecting a finger-down event followed by detecting one or morefinger-dragging events, and subsequently followed by detecting afinger-up (lift off) event.

Graphics module 132 includes various known software components forrendering and displaying graphics on touch screen 112 or other display,including components for changing the intensity of graphics that aredisplayed. As used herein, the term “graphics” includes any object thatcan be displayed to a user, including without limitation text, webpages, icons (such as user-interface objects including soft keys),digital images, videos, animations and the like.

In some embodiments, graphics module 132 stores data representinggraphics to be used. Each graphic may be assigned a corresponding code.Graphics module 132 receives, from applications etc., one or more codesspecifying graphics to be displayed along with, if necessary, coordinatedata and other graphic property data, and then generates screen imagedata to output to display controller 156.

Text input module 134, which may be a component of graphics module 132,provides soft keyboards for entering text in various applications (e.g.,contacts 137, e-mail 140, IM 141, browser 147, and any other applicationthat needs text input).

GPS module 135 determines the location of the device and provides thisinformation for use in various applications (e.g., to telephone 138 foruse in location-based dialing, to camera 143 as picture/video metadata,and to applications that provide location-based services such as weatherwidgets, local yellow page widgets, and map/navigation widgets).

Applications 136 may include the following modules (or sets ofinstructions), or a subset or superset thereof:

-   -   contacts module 137 (sometimes called an address book or contact        list);    -   telephone module 138;    -   video conferencing module 139;    -   e-mail client module 140;    -   instant messaging (IM) module 141;    -   workout support module 142;    -   camera module 143 for still and/or video images;    -   image management module 144;    -   video player module 145;    -   music player module 146;    -   browser module 147;    -   calendar module 148;    -   widget modules 149, which may include one or more of: weather        widget 149-1, stocks widget 149-2, calculator widget 149-3,        alarm clock widget 149-4, dictionary widget 149-5, and other        widgets obtained by the user, as well as user-created widgets        149-6;    -   widget creator module 150 for making user-created widgets 149-6;    -   search module 151;    -   video and music player module 152, which merges video player        module 145 and music player module 146;    -   notes module 153;    -   map module 154; and/or    -   online video module 155.

Examples of other applications 136 that may be stored in memory 102include other word processing applications, other image editingapplications, drawing applications, presentation applications,JAVA-enabled applications, encryption, digital rights management, voicerecognition, and voice replication.

In conjunction with touch screen 112, display controller 156, contactmodule 130, graphics module 132, and text input module 134, contactsmodule 137 may be used to manage an address book or contact list (e.g.,stored in application internal state 192 of contacts module 137 inmemory 102 or memory 370), including: adding name(s) to the addressbook; deleting name(s) from the address book; associating telephonenumber(s), e-mail address(es), physical address(es) or other informationwith a name; associating an image with a name; categorizing and sortingnames; providing telephone numbers or e-mail addresses to initiateand/or facilitate communications by telephone 138, video conference 139,e-mail 140, or IM 141; and so forth.

In conjunction with RF circuitry 108, audio circuitry 110, speaker 111,microphone 113, touch screen 112, display controller 156, contact module130, graphics module 132, and text input module 134, telephone module138 may be used to enter a sequence of characters corresponding to atelephone number, access one or more telephone numbers in address book137, modify a telephone number that has been entered, dial a respectivetelephone number, conduct a conversation and disconnect or hang up whenthe conversation is completed. As noted above, the wirelesscommunication may use any of a plurality of communications standards,protocols and technologies.

In conjunction with RF circuitry 108, audio circuitry 110, speaker 111,microphone 113, touch screen 112, display controller 156, optical sensor164, optical sensor controller 158, contact module 130, graphics module132, text input module 134, contact list 137, and telephone module 138,videoconferencing module 139 includes executable instructions toinitiate, conduct, and terminate a video conference between a user andone or more other participants in accordance with user instructions.

In conjunction with RF circuitry 108, touch screen 112, displaycontroller 156, contact module 130, graphics module 132, and text inputmodule 134, e-mail client module 140 includes executable instructions tocreate, send, receive, and manage e-mail in response to userinstructions. In conjunction with image management module 144, e-mailclient module 140 makes it very easy to create and send e-mails withstill or video images taken with camera module 143.

In conjunction with RF circuitry 108, touch screen 112, displaycontroller 156, contact module 130, graphics module 132, and text inputmodule 134, the instant messaging module 141 includes executableinstructions to enter a sequence of characters corresponding to aninstant message, to modify previously entered characters, to transmit arespective instant message (for example, using a Short Message Service(SMS) or Multimedia Message Service (MMS) protocol for telephony-basedinstant messages or using XMPP, SIMPLE, or IMPS for Internet-basedinstant messages), to receive instant messages and to view receivedinstant messages. In some embodiments, transmitted and/or receivedinstant messages may include graphics, photos, audio files, video filesand/or other attachments as are supported in a MMS and/or an EnhancedMessaging Service (EMS). As used herein, “instant messaging” refers toboth telephony-based messages (e.g., messages sent using SMS or MMS) andInternet-based messages (e.g., messages sent using XMPP, SIMPLE, orIMPS).

In conjunction with RF circuitry 108, touch screen 112, displaycontroller 156, contact module 130, graphics module 132, text inputmodule 134, GPS module 135, map module 154, and music player module 146,workout support module 142 includes executable instructions to createworkouts (e.g., with time, distance, and/or calorie burning goals);communicate with workout sensors (sports devices); receive workoutsensor data; calibrate sensors used to monitor a workout; select andplay music for a workout; and display, store and transmit workout data.

In conjunction with touch screen 112, display controller 156, opticalsensor(s) 164, optical sensor controller 158, contact module 130,graphics module 132, and image management module 144, camera module 143includes executable instructions to capture still images or video(including a video stream) and store them into memory 102, modifycharacteristics of a still image or video, or delete a still image orvideo from memory 102.

In conjunction with touch screen 112, display controller 156, contactmodule 130, graphics module 132, text input module 134, and cameramodule 143, image management module 144 includes executable instructionsto arrange, modify (e.g., edit), or otherwise manipulate, label, delete,present (e.g., in a digital slide show or album), and store still and/orvideo images.

In conjunction with touch screen 112, display controller 156, contactmodule 130, graphics module 132, audio circuitry 110, and speaker 111,video player module 145 includes executable instructions to display,present or otherwise play back videos (e.g., on touch screen 112 or onan external, connected display via external port 124).

In conjunction with touch screen 112, display system controller 156,contact module 130, graphics module 132, audio circuitry 110, speaker111, RF circuitry 108, and browser module 147, music player module 146includes executable instructions that allow the user to download andplay back recorded music and other sound files stored in one or morefile formats, such as MP3 or AAC files. In some embodiments, device 100may include the functionality of an MP3 player, such as an iPod(trademark of Apple Inc.).

In conjunction with RF circuitry 108, touch screen 112, display systemcontroller 156, contact module 130, graphics module 132, and text inputmodule 134, browser module 147 includes executable instructions tobrowse the Internet in accordance with user instructions, includingsearching, linking to, receiving, and displaying web pages or portionsthereof, as well as attachments and other files linked to web pages.

In conjunction with RF circuitry 108, touch screen 112, display systemcontroller 156, contact module 130, graphics module 132, text inputmodule 134, e-mail client module 140, and browser module 147, calendarmodule 148 includes executable instructions to create, display, modify,and store calendars and data associated with calendars (e.g., calendarentries, to do lists, etc.) in accordance with user instructions.

In conjunction with RF circuitry 108, touch screen 112, display systemcontroller 156, contact module 130, graphics module 132, text inputmodule 134, and browser module 147, widget modules 149 aremini-applications that may be downloaded and used by a user (e.g.,weather widget 149-1, stocks widget 149-2, calculator widget 149-3,alarm clock widget 149-4, and dictionary widget 149-5) or created by theuser (e.g., user-created widget 149-6). In some embodiments, a widgetincludes an HTML (Hypertext Markup Language) file, a CSS (CascadingStyle Sheets) file, and a JavaScript file. In some embodiments, a widgetincludes an XML (Extensible Markup Language) file and a JavaScript file(e.g., Yahoo! Widgets).

In conjunction with RF circuitry 108, touch screen 112, display systemcontroller 156, contact module 130, graphics module 132, text inputmodule 134, and browser module 147, the widget creator module 150 may beused by a user to create widgets (e.g., turning a user-specified portionof a web page into a widget).

In conjunction with touch screen 112, display system controller 156,contact module 130, graphics module 132, and text input module 134,search module 151 includes executable instructions to search for text,music, sound, image, video, and/or other files in memory 102 that matchone or more search criteria (e.g., one or more user-specified searchterms) in accordance with user instructions.

In conjunction with touch screen 112, display controller 156, contactmodule 130, graphics module 132, and text input module 134, notes module153 includes executable instructions to create and manage notes, to dolists, and the like in accordance with user instructions.

In conjunction with RF circuitry 108, touch screen 112, display systemcontroller 156, contact module 130, graphics module 132, text inputmodule 134, GPS module 135, and browser module 147, map module 154 maybe used to receive, display, modify, and store maps and data associatedwith maps (e.g., driving directions; data on stores and other points ofinterest at or near a particular location; and other location-baseddata) in accordance with user instructions.

In conjunction with touch screen 112, display system controller 156,contact module 130, graphics module 132, audio circuitry 110, speaker111, RF circuitry 108, text input module 134, e-mail client module 140,and browser module 147, online video module 155 includes instructionsthat allow the user to access, browse, receive (e.g., by streamingand/or download), play back (e.g., on the touch screen or on anexternal, connected display via external port 124), send an e-mail witha link to a particular online video, and otherwise manage online videosin one or more file formats, such as H.264. In some embodiments, instantmessaging module 141, rather than e-mail client module 140, is used tosend a link to a particular online video. Additional description of theonline video application can be found in U.S. Provisional PatentApplication No. 60/936,562, “Portable Multifunction Device, Method, andGraphical User Interface for Playing Online Videos,” filed Jun. 20,2007, and U.S. patent application Ser. No. 11/968,067, “PortableMultifunction Device, Method, and Graphical User Interface for PlayingOnline Videos,” filed Dec. 31, 2007, the content of which is herebyincorporated by reference in its entirety.

Each of the above identified modules and applications correspond to aset of executable instructions for performing one or more functionsdescribed above and the methods described in this application (e.g., thecomputer-implemented methods and other information processing methodsdescribed herein). These modules (i.e., sets of instructions) need notbe implemented as separate software programs, procedures or modules, andthus various subsets of these modules may be combined or otherwisere-arranged in various embodiments. For example, video player module 145may be combined with music player module 146 into a single module (e.g.,video and music player module 152, FIG. 1B). In some embodiments, memory102 may store a subset of the modules and data structures identifiedabove. Furthermore, memory 102 may store additional modules and datastructures not described above.

In some embodiments, device 100 is a device where operation of apredefined set of functions on the device is performed exclusivelythrough a touch screen and/or a touchpad. By using a touch screen and/ora touchpad as the primary input control device for operation of device100, the number of physical input control devices (such as push buttons,dials, and the like) on device 100 may be reduced.

The predefined set of functions that may be performed exclusivelythrough a touch screen and/or a touchpad include navigation between userinterfaces. In some embodiments, the touchpad, when touched by the user,navigates device 100 to a main, home, or root menu from any userinterface that may be displayed on device 100. In such embodiments, thetouchpad may be referred to as a “menu button.” In some otherembodiments, the menu button may be a physical push button or otherphysical input control device instead of a touchpad.

FIG. 1C is a block diagram illustrating exemplary components for eventhandling in accordance with some embodiments. In some embodiments,memory 102 (in FIGS. 1A and 1B) or 370 (FIG. 3) includes event sorter170 (e.g., in operating system 126) and a respective application 136-1(e.g., any of the aforementioned applications 137-151, 155, 380-390).

Event sorter 170 receives event information and determines theapplication 136-1 and application view 191 of application 136-1 to whichto deliver the event information. Event sorter 170 includes eventmonitor 171 and event dispatcher module 174. In some embodiments,application 136-1 includes application internal state 192, whichindicates the current application view(s) displayed on touch sensitivedisplay 112 when the application is active or executing. In someembodiments, device/global internal state 157 is used by event sorter170 to determine which application(s) is(are) currently active, andapplication internal state 192 is used by event sorter 170 to determineapplication views 191 to which to deliver event information.

In some embodiments, application internal state 192 includes additionalinformation, such as one or more of: resume information to be used whenapplication 136-1 resumes execution, user interface state informationthat indicates information being displayed or that is ready for displayby application 136-1, a state queue for enabling the user to go back toa prior state or view of application 136-1, and a redo/undo queue ofprevious actions taken by the user.

Event monitor 171 receives event information from peripherals interface118. Event information includes information about a sub-event (e.g., auser touch on touch-sensitive display 112, as part of a multi-touchgesture). Peripherals interface 118 transmits information it receivesfrom I/O subsystem 106 or a sensor, such as proximity sensor 166,accelerometer(s) 168, and/or microphone 113 (through audio circuitry110). Information that peripherals interface 118 receives from I/Osubsystem 106 includes information from touch-sensitive display 112 or atouch-sensitive surface.

In some embodiments, event monitor 171 sends requests to the peripheralsinterface 118 at predetermined intervals. In response, peripheralsinterface 118 transmits event information. In other embodiments,peripheral interface 118 transmits event information only when there isa significant event (e.g., receiving an input beyond a predeterminednoise threshold and/or for more than a predetermined duration).

In some embodiments, event sorter 170 also includes a hit viewdetermination module 172 and/or an active event recognizer determinationmodule 173.

Hit view determination module 172 provides software procedures fordetermining where a sub-event has taken place within one or more views,when touch sensitive display 112 displays more than one view. Views aremade up of controls and other elements that a user can see on thedisplay.

Another aspect of the user interface associated with an application is aset views, sometimes herein called application views or user interfacewindows, in which information is displayed and touch-based gesturesoccur. The application views (of a respective application) in which atouch is detected may correspond to programmatic levels within aprogrammatic or view hierarchy of the application. For example, thelowest level view in which a touch is detected may be called the hitview, and the set of events that are recognized as proper inputs may bedetermined based, at least in part, on the hit view of the initial touchthat begins a touch-based gesture.

Hit view determination module 172 receives information related tosub-events of a touch-based gesture. When an application has multipleviews organized in a hierarchy, hit view determination module 172identifies a hit view as the lowest view in the hierarchy which shouldhandle the sub-event. In most circumstances, the hit view is the lowestlevel view in which an initiating sub-event occurs (i.e., the firstsub-event in the sequence of sub-events that form an event or potentialevent). Once the hit view is identified by the hit view determinationmodule, the hit view typically receives all sub-events related to thesame touch or input source for which it was identified as the hit view.

Active event recognizer determination module 173 determines which viewor views within a view hierarchy should receive a particular sequence ofsub-events. In some embodiments, active event recognizer determinationmodule 173 determines that only the hit view should receive a particularsequence of sub-events. In other embodiments, active event recognizerdetermination module 173 determines that all views that include thephysical location of a sub-event are actively involved views, andtherefore determines that all actively involved views should receive aparticular sequence of sub-events. In other embodiments, even if touchsub-events were entirely confined to the area associated with oneparticular view, views higher in the hierarchy would still remain asactively involved views.

Event dispatcher module 174 dispatches the event information to an eventrecognizer (e.g., event recognizer 180). In embodiments including activeevent recognizer determination module 173, event dispatcher module 174delivers the event information to an event recognizer determined byactive event recognizer determination module 173. In some embodiments,event dispatcher module 174 stores in an event queue the eventinformation, which is retrieved by a respective event receiver module182.

In some embodiments, operating system 126 includes event sorter 170.Alternatively, application 136-1 includes event sorter 170. In yet otherembodiments, event sorter 170 is a stand-alone module, or a part ofanother module stored in memory 102, such as contact/motion module 130.

In some embodiments, application 136-1 includes one or more applicationviews 191, each of which includes instructions for handling touch eventsthat occur within a respective view of the application's user interface.Each application view 191 of the application 136-1 includes one or moreevent recognizers 180 and one or more event handlers 190. Typically, arespective application view 191 includes a plurality of eventrecognizers 180 and a plurality of event handlers 190. In otherembodiments, one or more of event recognizers 180 are part of a separatemodule, such as a user interface kit (not shown) or a higher levelobject from which application 136-1 inherits methods and otherproperties. In some embodiments, a respective application view 191 alsoincludes one or more of: data updater 176, object updater 177, GUIupdater 178, and/or event data 179 received from event sorter 170.

A respective event recognizer 180 receives event information (e.g.,event data 179) from event sorter 170, and identifies an event from theevent information. Event recognizer 180 includes event receiver 182 andevent comparator 184. In some embodiments, event recognizer 180 alsoincludes at least a subset of: metadata 183, and event deliveryinstructions 188 (which may include sub-event delivery instructions).

Event receiver 182 receives event information from event sorter 170. Theevent information includes information about a sub-event, for example, atouch or a touch movement. Depending on the sub-event, the eventinformation also includes additional information, such as location ofthe sub-event. When the sub-event concerns motion of a touch the eventinformation may also include speed and direction of the sub-event. Insome embodiments, events include rotation of the device from oneorientation to another (e.g., from a portrait orientation to a landscapeorientation, or vice versa), and the event information includescorresponding information about the current orientation (also calleddevice attitude) of the device.

Event comparator 184 compares the event information to predefined eventor sub-event definitions and, based on the comparison, determines anevent or sub-event, or determines or updates the state of an event orsub-event. In some embodiments, event comparator 184 includes eventdefinitions 186. Event definitions 186 contain definitions of events(e.g., predefined sequences of sub-events), for example, event 1(187-1), event 2 (187-2), and others. In some embodiments, sub-events inan event 187 include, for example, touch begin, touch end, touchmovement, touch cancellation, and multiple touching. In one example, thedefinition for event 1 (187-1) is a double tap on a displayed object.The double tap, for example, comprises a first touch (touch begin) onthe displayed object for a predetermined phase, a first lift-off (touchend) for a predetermined phase, a second touch (touch begin) on thedisplayed object for a predetermined phase, and a second lift-off (touchend) for a predetermined phase. In another example, the definition forevent 2 (187-2) is a dragging on a displayed object. The dragging, forexample, comprises a touch (or contact) on the displayed object for apredetermined phase, a movement of the touch across touch-sensitivedisplay 112, and lift-off of the touch (touch end). In some embodiments,the event also includes information for the event's associated eventhandlers 190.

In some embodiments, event definition 187 includes a definition of anevent for a respective user-interface object. In some embodiments, eventcomparator 184 performs a hit test to determine which user-interfaceobject is associated with a sub-event. For example, in an applicationview in which three user-interface objects are displayed ontouch-sensitive display 112, when a touch is detected on touch-sensitivedisplay 112, event comparator 184 performs a hit test to determine whichof the three user-interface objects is associated with the touch(sub-event). If each displayed object is associated with a respectiveevent handler 190, the event comparator uses the result of the hit testto determine which event handler 190 should be activated. For example,event comparator 184 selects an event handler associated with thesub-event and the object triggering the hit test.

In some embodiments, the definition for a respective event 187 alsoincludes delayed actions that delay delivery of the event informationuntil after it has been determined whether the sequence of sub-eventsdoes or does not correspond to the event recognizer's event type.

When a respective event recognizer 180 determines that the series ofsub-events do not match any of the events in event definitions 186, therespective event recognizer 180 enters an event impossible or eventcancel state, after which it disregards subsequent sub-events of thetouch-based gesture. In this situation, other event recognizers, if any,that remain active for the hit view continue to track and processsub-events of an ongoing touch-based gesture.

In some embodiments, a respective event recognizer 180 includes metadata183 with configurable properties, flags, and/or lists that indicate howthe event delivery system should perform sub-event delivery to activelyinvolved event recognizers. In some embodiments, metadata 183 includesconfigurable properties, flags, and/or lists that indicate how eventrecognizers may interact with one another. In some embodiments, metadata183 includes configurable properties, flags, and/or lists that indicatewhether sub-events are delivered to varying levels in the view orprogrammatic hierarchy.

In some embodiments, a respective event recognizer 180 activates eventhandler 190 associated with an event when one or more particularsub-events of an event are recognized. In some embodiments, a respectiveevent recognizer 180 delivers event information associated with theevent to event handler 190. Activating an event handler 190 is distinctfrom sending (and deferred sending) sub-events to a respective hit view.In some embodiments, event recognizer 180 throws a flag associated withthe recognized event, and event handler 190 associated with the flagcatches the flag and performs a predefined process.

In some embodiments, event delivery instructions 188 includes sub-eventdelivery instructions that deliver event information about a sub-eventwithout activating an event handler. Instead, the sub-event deliveryinstructions deliver event information to event handlers associated withthe series of sub-events or to actively involved views. Event handlersassociated with the series of sub-events or with actively involved viewsreceive the event information and perform a predetermined process.

In some embodiments, data updater 176 creates and updates data used inapplication 136-1. For example, data updater 176 updates the telephonenumber used in contacts module 137, or stores a video file used in videoplayer module 145. In some embodiments, object updater 177 creates andupdates objects used in application 136-1. For example, object updater176 creates a new user-interface object or updates the position of auser-interface object. GUI updater 178 updates the GUI. For example, GUIupdater 178 prepares display information and sends it to graphics module132 for display on a touch-sensitive display.

In some embodiments, event handler(s) 190 includes or has access to dataupdater 176, object updater 177, and GUI updater 178. In someembodiments, data updater 176, object updater 177, and GUI updater 178are included in a single module of a respective application 136-1 orapplication view 191. In other embodiments, they are included in two ormore software modules.

It shall be understood that the foregoing discussion regarding eventhandling of user touches on touch-sensitive displays also applies toother forms of user inputs to operate multifunction devices 100 withinput-devices, not all of which are initiated on touch screens, e.g.,coordinating mouse movement and mouse button presses with or withoutsingle or multiple keyboard presses or holds, user movements taps,drags, scrolls, etc., on touch-pads, pen stylus inputs, movement of thedevice, oral instructions, detected eye movements, biometric inputs,and/or any combination thereof, which may be utilized as inputscorresponding to sub-events which define an event to be recognized.

FIG. 2 illustrates a portable multifunction device 100 having a touchscreen 112 in accordance with some embodiments. The touch screen maydisplay one or more graphics within user interface (UI) 200. In thisembodiment, as well as others described below, a user may select one ormore of the graphics by making contact or touching the graphics, forexample, with one or more fingers 202 (not drawn to scale in the figure)or one or more styluses 203 (not drawn to scale in the figure). In someembodiments, selection of one or more graphics occurs when the userbreaks contact with the one or more graphics. In some embodiments, thecontact may include a gesture, such as one or more taps, one or moreswipes (from left to right, right to left, upward and/or downward)and/or a rolling of a finger (from right to left, left to right, upwardand/or downward) that has made contact with device 100. In someembodiments, inadvertent contact with a graphic may not select thegraphic. For example, a swipe gesture that sweeps over an applicationicon may not select the corresponding application when the gesturecorresponding to selection is a tap.

Device 100 may also include one or more physical buttons, such as “home”or menu button 204. As described previously, menu button 204 may be usedto navigate to any application 136 in a set of applications that may beexecuted on device 100. Alternatively, in some embodiments, the menubutton is implemented as a soft key in a GUI displayed on touch screen112.

In one embodiment, device 100 includes touch screen 112, menu button204, push button 206 for powering the device on/off and locking thedevice, volume adjustment button(s) 208, Subscriber Identity Module(SIM) card slot 210, head set jack 212, and docking/charging externalport 124. Push button 206 may be used to turn the power on/off on thedevice by depressing the button and holding the button in the depressedstate for a predefined time interval; to lock the device by depressingthe button and releasing the button before the predefined time intervalhas elapsed; and/or to unlock the device or initiate an unlock process.In an alternative embodiment, device 100 also may accept verbal inputfor activation or deactivation of some functions through microphone 113.

FIG. 3 is a block diagram of an exemplary multifunction device with adisplay and a touch-sensitive surface in accordance with someembodiments. Device 300 need not be portable. In some embodiments,device 300 is a laptop computer, a desktop computer, a tablet computer,a multimedia player device, a navigation device, an educational device(such as a child's learning toy), a gaming system, or a control device(e.g., a home or industrial controller). Device 300 typically includesone or more processing units (CPU's) 310, one or more network or othercommunications interfaces 360, memory 370, and one or more communicationbuses 320 for interconnecting these components. Communication buses 320may include circuitry (sometimes called a chipset) that interconnectsand controls communications between system components. Device 300includes input/output (I/O) interface 330 comprising display 340, whichis typically a touch screen display. I/O interface 330 also may includea keyboard and/or mouse (or other pointing device) 350 and touchpad 355.Memory 370 includes high-speed random access memory, such as DRAM, SRAM,DDR RAM or other random access solid state memory devices; and mayinclude non-volatile memory, such as one or more magnetic disk storagedevices, optical disk storage devices, flash memory devices, or othernon-volatile solid state storage devices. Memory 370 may optionallyinclude one or more storage devices remotely located from CPU(s) 310. Insome embodiments, memory 370 stores programs, modules, and datastructures analogous to the programs, modules, and data structuresstored in memory 102 of portable multifunction device 100 (FIG. 1), or asubset thereof. Furthermore, memory 370 may store additional programs,modules, and data structures not present in memory 102 of portablemultifunction device 100. For example, memory 370 of device 300 maystore drawing module 380, presentation module 382, word processingmodule 384, website creation module 386, disk authoring module 388,and/or spreadsheet module 390, while memory 102 of portablemultifunction device 100 (FIG. 1) may not store these modules.

Each of the above identified elements in FIG. 3 may be stored in one ormore of the previously mentioned memory devices. Each of the aboveidentified modules corresponds to a set of instructions for performing afunction described above. The above identified modules or programs(i.e., sets of instructions) need not be implemented as separatesoftware programs, procedures or modules, and thus various subsets ofthese modules may be combined or otherwise re-arranged in variousembodiments. In some embodiments, memory 370 may store a subset of themodules and data structures identified above. Furthermore, memory 370may store additional modules and data structures not described above.

Attention is now directed towards embodiments of user interfaces (“UI”)that may be implemented on portable multifunction device 100.

FIGS. 4A and 4B illustrate exemplary user interfaces for a menu ofapplications on portable multifunction device 100 in accordance withsome embodiments. Similar user interfaces may be implemented on device300. In some embodiments, user interface 400A includes the followingelements, or a subset or superset thereof:

-   -   Signal strength indicator(s) 402 for wireless communication(s),        such as cellular and Wi-Fi signals;    -   Time 404;    -   Bluetooth indicator 405;    -   Battery status indicator 406;    -   Tray 408 with icons for frequently used applications, such as:        -   Phone 138, which may include an indicator 414 of the number            of missed calls or voicemail messages;        -   E-mail client 140, which may include an indicator 410 of the            number of unread e-mails;        -   Browser 147; and        -   Music player 146; and    -   Icons for other applications, such as:        -   IM 141;        -   Image management 144;        -   Camera 143;        -   Video player 145;        -   Weather 149-1;        -   Stocks 149-2;        -   Workout support 142;        -   Calendar 148;        -   Calculator 149-3;        -   Alarm clock 149-4;        -   Dictionary 149-5; and        -   User-created widget 149-6.

In some embodiments, user interface 400B includes the followingelements, or a subset or superset thereof:

-   -   402, 404, 405, 406, 141, 148, 144, 143, 149-3, 149-2, 149-1,        149-4, 410, 414, 138, 140, and 147, as described above;    -   Map 154;    -   Notes 153;    -   Settings 412, which provides access to settings for device 100        and its various applications 136, as described further below;    -   Video and music player module 152, also referred to as iPod        (trademark of Apple Inc.) module 152; and    -   Online video module 155, also referred to as YouTube (trademark        of Google Inc.) module 155.

FIG. 4C illustrates an exemplary user interface on a device (e.g.,device 300, FIG. 3) with a touch-sensitive surface 451 (e.g., a tabletor touchpad 355, FIG. 3) that is separate from the display 450 (e.g.,touch screen display 112). Although many of the examples which followwill be given with reference to inputs on touch screen display 112(where the touch sensitive surface and the display are combined), insome embodiments, the device detects inputs on a touch-sensitive surfacethat is separate from the display, as shown in FIG. 4C. In someembodiments the touch sensitive surface (e.g., 451 in FIG. 4C) has aprimary axis (e.g., 452 in FIG. 4C) that corresponds to a primary axis(e.g., 453 in FIG. 4C) on the display (e.g., 450). In accordance withthese embodiments, the device detects contacts (e.g., 460 and 462 inFIG. 4C) with the touch-sensitive surface 451 at locations thatcorrespond to respective locations on the display (e.g., in FIG. 4C 460corresponds to 468 and 462 corresponds to 470). In this way, user inputs(e.g., contacts 460 and 462, and movements thereof) detected by thedevice on the touch-sensitive surface (e.g., 451 in FIG. 4C) are used bythe device to manipulate the user interface on the display (e.g., 450 inFIG. 4C) of the multifunction device when the touch-sensitive surface isseparate from the display. It should be understood that similar methodsmay be used for other user interfaces described herein.

Additionally, while the following examples are given primarily withreference to finger inputs (e.g., finger contacts, finger tap gestures,finger swipe gestures), it should be understood that, in someembodiments, one or more of the finger inputs are replaced with inputfrom another input device (e.g., a mouse based input or stylus input).For example, a swipe gesture may be replaced with a mouse click (e.g.,instead of a contact) followed by movement of the cursor along the pathof the swipe (e.g., instead of movement of the contact). As anotherexample, a tap gesture may be replaced with a mouse click while thecursor is located over the location of the tap gesture (e.g., instead ofdetection of the contact followed by ceasing to detect the contact).Similarly, when multiple user inputs are simultaneously detected, itshould be understood that multiple computer mice may be usedsimultaneously, or a mouse and finger contacts may be usedsimultaneously.

Attention is now directed towards embodiments of user interfaces (“UI”)and associated processes that may be implemented on a computing devicewith a display and a touch-sensitive surface, such as portablemultifunction device 100 of FIG. 1A, 4A, or 5A, or device 300 of FIG. 3.

FIGS. 5A-5M illustrate exemplary user interfaces for manipulating userinterface objects with velocity sensitive alignment guides in accordancewith some embodiments. The user interfaces in these figures are used toillustrate the processes described below, including the processes inFIGS. 6A-6C.

UI 500A (FIG. 5A) depicts an exemplary user interface UI 500A displayedon device 100. In this example, the user interface includes anelectronic canvas 500 with user interface elements displayed as moveableobjects, i.e., rectangle 502 and diamond 503. Near a corner of rectangle502, a user has made, and the device has detected, a single fingercontact 505 on the touch screen 112.

UI 500A also depicts that device 100 detects the start of a usergesture, i.e., user gesture 507-1 on touch screen 112; user gesture507-1 is a gesture to move rectangle 502.

UI 500A is in a first state with respect to the display of a pluralityof alignment guides adapted to indicate potential placement positionswithin the user interface for user interface elements. Generally, in thefirst state, alignment guides are not visibly displayed in the userinterface, while in the second state, alignment guides are visiblydisplayed in the user interface. Further explanation and examples of thefirst and second user interface states are provided below.

Additionally, though not directly illustrated in UI 500A, the devicedetermines that the velocity of user gesture 507-1 is less than a firstpredefined velocity threshold, which in this exemplary embodiment is 400pixels per second.

UI 500B (FIG. 5B) illustrates that, after detecting user gesture 507-1in UI 500A and determining that the velocity of user gesture 507-1 isless than the first predefined velocity threshold, the user interfaceenters a second state with respect to displaying alignment guides. Asdepicted in the exemplary user interface of UI 500B, the device visiblydisplays some possible alignment guides in conjunction with thedisplayed objects rectangle 502 and diamond 503 (i.e., alignment guides502-a and 502-b with respect to rectangle 502; and alignment guides503-a, 503-b, and 503-c with respect to diamond 503). Alignment guides502-b, 503-a, 503-b, and 503-c are configured with first attractionstrengths. In these exemplary user interface figures, the attractionstrengths for alignment guides 502-b, 503-a, 503-b, and 503-c are set to100%, 100%, 75%, and 100%, respectively. For purposes of illustration,these attraction strength values are displayed in conjunction with thereference numerals for alignment guides 502-b, 503-a, 503-b, and 503-c.

UI 500B also illustrates that in response to detecting user gesture507-1 in UI 500A, the device initiated movement of rectangle 502 withinthe user interface, i.e., on the electronic canvas 500, in accordancewith user gesture 507-1.

UI 500B also illustrates that, in the second state of the userinterface, rulers 504-1 and 504-2 are displayed, and placement marks504-1 p and 504-2 p are displayed in conjunction with rulers 504-1 and504-2. Placement marks 504-1 p and 504-2 p correspond to the relativelocation of alignment guides 502-b and 502-a, respectively. Thoughplacement marks are displayed in many embodiments (though not allembodiments), for purposes of brevity and clarity, the remainingexemplary user interface figures will omit these marks.

UI 500C (FIG. 5C) illustrates that after user gesture 507-1 in UI 500Aand UI 500B, rectangle 502 is snapped to alignment guide 502-b.

UI 500C also illustrates that after rectangle 502 was snapped toalignment guide 502-b, user gesture 507-2 is detected. Though notdirectly illustrated in UI 500C, the device determines that the velocityof user gesture 507-2 is greater than a predefined velocity threshold.

UI 500D (FIG. 5D) illustrates that in response to user gesture 507-2,rectangle 502 has been moved in accordance with user gesture 507-2.

In UI 500D, the user interface is again in the first state with respectto displaying alignment guides because the velocity of user gesture507-2 exceeds the predefined velocity threshold. Solely for purposes ofillustration, alignment guides 502-c, 502-d, 503-a, 503-b, and 503-c aredisplayed in FIG. 5D at a reduced level of darkness to represent theirlocation, but subject to limited exceptions, these guides are notdisplayed visibly when the user interface is in the first state.

As the velocity of user gesture 507-2 exceeds the predefined velocitythreshold, alignment guides 502-c and 502-d are configured with anattraction strength of 0%, while alignment guides 503-a, 503-b, and503-c are reconfigured with a second attraction strength, also 0%. Ascan be seen, for alignment guides 503-a, 503-b, and 503-c, the firstattraction strength as depicted in UI 500B was greater than zero, whilein UI 500D, where the user interface is again in the first state,alignment guides 503-a, 503-b, and 503-c are reconfigured with thesecond attraction strength of 0%.

UI 500E (FIG. 5E) illustrates that, in accordance with user gesture507-2 (depicted in UI 500C and UI 500D), rectangle 502 has been movedpast alignment guides 502-c and 502-d without snapping to either guide.This is because the guides' attraction strengths are set to zero.

As with UI 500D, alignment guides 502-c, 502-d, 503-a, 503-b, and 503-care displayed in FIG. 5E at a reduced level of darkness to representtheir location, but these guides are not generally displayed visiblywhen the user interface is in the first state.

Though not illustrated directly in UI 500D, single finger contact 505 isremoved from touch screen 112, and therefore, user gesture 507 isterminated.

UI 500F (FIG. 5F) illustrates that after user gesture 507 is terminated,the user interface is in the first state, and no alignment guides orrulers are visibly displayed.

UI 500G (FIG. 5G) depicts that a single finger contact 510 is detectedover rectangle 502. Generally, alignment guides are visibly displayedwhen the beginning of a user gesture is detected, and as such, alignmentguides 502-e, 503-d, 503-e, and 503-f are visibly displayed. Alignmentguides 502-e, 503-d, 503-e, and 503-f are configured with a firstattraction strength, i.e., 100%.

UI 500G also illustrates exemplary user gesture 512-1, which is agesture to move user interface element rectangle 502.

In UI 500G, rectangle 502 is substantially aligned on an axis withdiamond 503, i.e., the axis that corresponds to visibly displayedalignment guide 503-e.

Though not directly illustrated in UI 500G, the device determines thatthe velocity of user gesture 512-1 is greater than a predefined velocitythreshold.

UI 500H (FIG. 5H) illustrates that because the velocity of user gesture512-1 was greater than the predefined velocity threshold, alignmentguides 502-e, 503-d, and 503-f are not visibly displayed (as in UI 500Dand UI 500E, alignment guides 502-e, 503-d, and 503-f are displayed inFIG. 5H at a reduced level of darkness merely to represent theirlocation).

Additionally, because the velocity of user gesture 512-1 was greaterthan the predefined velocity threshold, alignment guides 502-e, 503-d,and 503-f are configured with a second attraction strength, i.e., 0%.

Alignment guide 503-e, however, is visibly displayed in UI 500H, andalignment guide 503-e retains its first attraction strength of 100%; insome embodiments when a user gesture is moving a first object towards asecond object that is on a common axis with the first object, analignment guide associated with the common axis is visibly displayedeven though the user gesture velocity exceeded the predefined velocitythreshold.

UI 500H illustrates that rectangle 502 has been moved along alignmentguide 503-e in accordance with user gesture 512-1, and has passeddirectly through alignment guide 502-e, which is set with an attractionstrength of zero. Accordingly, when an alignment guide's attractionstrength is set to zero, an object is moved in accordance with a usergesture even when the object is closer than a predefined distance to atarget alignment guide.

UI 500I (FIG. 5I) illustrates that single finger contact 510 has stoppedmoving. Though not directly illustrated, the device detected a period ofuser gesture inactivity exceeding a predefined duration, specifically,single finger contact 510 remained in substantially the same locationfor 0.2 seconds.

UI 500J (FIG. 5J) illustrates that, after the period of user gestureinactivity depicted in UI 500I, the state of the user interface ischanged. Specifically, in this example, alignment guides 502-f, 503-d,and 503-f are visibly displayed, and their attraction strengths areconfigured to be 100%; alignment guide 503-e continues to be visiblydisplayed, and its attraction strength remains at 100%.

UI 500J also illustrates exemplary user gesture 512-2. Though notdirectly illustrated in UI 500J, the device determines that the velocityof user gesture 512-2 is less than a predefined velocity threshold.

UI 500K (FIG. 5K) illustrates that in response to user gesture 512-2,rectangle 502 has been moved toward alignment guide 502-f.

For illustrative purposes, magnified region 508 of the area betweendiamond 503 and rectangle 502 is depicted. Magnified region 508 includesimages of visibly displayed alignment guide 502-f and rectangle 502, aswell as line 509 associated with alignment guide 502-E Line 509represents a predefined distance 509-d associated with alignment guide502-E In UI 500K, rectangle 502's position is closer to alignment guide502-f than the line 509, which represents the predefined distance 509-d.(Line 509 is not displayed in some embodiments.)

UI 500L (FIG. 5L) illustrates that rectangle 502 is snapped to alignmentguide 502-f since rectangle 502 was closer to alignment guide 502-f thanthe predefined distance 509-d, and alignment guide 502-f was configuredwith a first attraction strength, i.e., 100%.

Though not illustrated directly in UI 500L, single finger contact 510 isremoved from touch screen 112, and therefore, user gesture 512 isterminated.

UI 500M (FIG. 5M) illustrates that after user gesture 512 is terminated,and neither alignment guides nor rulers are visibly displayed.

FIGS. 6A-6B are flow diagrams illustrating a method of manipulating userinterface objects with velocity sensitive alignment guides in accordancewith some embodiments. The method 600 is performed at a computing device(e.g., device 300, FIG. 3, or portable multifunction device 100, FIG. 1)with a display and a touch-sensitive surface. In some embodiments, thedisplay is a touch screen display and the touch-sensitive surface is onthe display. In some embodiments, the display is separate from thetouch-sensitive surface. Some operations in method 600 may be combinedand/or the order of some operations may be changed. Further, someoperations in method 600 may be combined with operations in method 650.

As described below, the method 600 provides an intuitive way tomanipulate user interface objects. The method reduces the cognitiveburden on a user when manipulating user interface objects, therebycreating a more efficient human-machine interface. For battery-operatedcomputing devices, enabling a user to manipulate user interface objectsfaster and more efficiently conserves power and increases the timebetween battery charges.

The method 600 is performed at a computing device with a display and oneor more user input devices adapted to detect user gestures (e.g., FIG.5A portable multifunction device 100, FIG. 3 device 300). The devicedisplays a user interface in a first state, the user interface includingat least a user interface element configured to be moved resized, orotherwise adjusted within the user interface in response to usergestures while the user interface is displayed in the first state; theuser interface also includes a plurality of alignment guides adapted toindicate potential placement positions within the user interface foruser interface elements being moved resized, or otherwise adjusted (602)(e.g., FIG. 5A, UI 500A including rectangle 502, and not displayedvisibly in UI 500A, but depicted in FIG. 5B, UI 500B, possible alignmentguides in conjunction with the displayed objects rectangle 502 anddiamond 503, i.e., alignment guides 502-a and 502-b with respect torectangle 502; and alignment guides 503-a, 503-b, and 503-c with respectto diamond 503; see also FIG. 5F, UI 500F including rectangle 502, andnot displayed visibly in UI 500F, but depicted in FIG. 5G, UI 500G,possible alignment guides in conjunction with the displayed objectsrectangle 502 and diamond 503, i.e., alignment guide 502-e with respectto rectangle 502; and alignment guides 503-d, 503-e, and 503-f withrespect to diamond 503).

Generally, when there is no active gesture being detected to move,resize, or adjust the plurality of alignment guides, alignment guidesare not visibly displayed. Also, while the user interface is in thefirst state, alignment guides are generally not displayed visibly.

In some embodiments, the first state includes not displaying theplurality of alignment guides visibly (604) (e.g., FIG. 5A, possiblealignment guides are not displayed visibly in conjunction with thedisplayed objects rectangle 502 and diamond 503).

In some embodiments, the plurality of alignment guides includes one ormore alignment guide types selected from the group consisting ofedge-to-middle-slide alignment guides, edge-to-edge alignment guides,and middle-to-middle alignment guides, electronic canvas middlealignment guides, electronic canvas edge alignment guides, electroniccanvas top, bottom, left, and right margin alignment guides, thelocation of an arbitrarily defined split of an electronic canvas, e.g.an electronic canvas split into three regions, alignment guides definedwithin a document theme or master template, and user-defined alignmentguides (606).

In some embodiments, at least some of the plurality of alignment guidesare displayed in conjunction with the user interface element (608)(e.g., FIG. 5B, alignment guides are displayed in conjunction with thedisplayed objects rectangle 502 and diamond 503, i.e., alignment guides502-a and 502-b with respect to rectangle 502; and alignment guides503-a, 503-b, and 503-c with respect to diamond 503).

In some embodiments, the user interface element is displayed on anelectronic canvas (610) (e.g., FIG. 5A the user interface includes anelectronic canvas 500, which includes rectangle 502).

In some embodiments, the display and at least one of the one or moreuser input devices comprise a touch-screen display (612) (e.g., FIG. 5A,touch screen 112).

The device detects (614) a user gesture, e.g., a swipe, drag, pinch,depinch, or any suitable user gesture, the user gesture corresponding toa gesture to move, resize, or otherwise adjust, the user interfaceelement within the user interface (e.g., FIG. 5A, user gesture 507-1 isa gesture to move rectangle 502).

The device determines (616) a velocity of the user gesture (e.g., FIG.5A, the device determines that the velocity of user gesture 507-1 isless than a predefined velocity threshold; and as discussed below,velocity determinations may be implemented by event sorter 170, eventrecognizer 180, and event handler 190 by calculating velocity fromdistance and duration data from one or more user gesture events).

In some embodiments, the gesture velocity, or rate of movementthreshold, is calculated by dividing the distance moved by the durationof the movement(s), and determining that the value is greater than apredefined threshold, (e.g., 250, 300, 350, 400, 500, 750, 1000pixels/second, or any suitable value). The determination of gesturevelocity may use the movement of a contact on a touch-sensitive display,or the user gesture movement input from any suitable input device, suchas a mouse or stylus.

In response to detecting the user gesture, the device moves, resizes, orotherwise adjusts the user interface element within the user interfacein accordance with the user gesture (618) (e.g., FIG. 5B, illustratingthat in response to detecting user gesture 507-1 in FIG. 5A, the deviceinitiated movement of rectangle 502 within the user interface, i.e., onthe electronic canvas 500, in accordance with user gesture 507-1).

While moving, resizing, or otherwise adjusting the user interfaceelement within the user interface, and when the velocity of the usergesture is less than or equal to a predefined velocity threshold (e.g.,250, 300, 350, 400, 500, 750, 1000 pixels/second, or any suitablevalue), the device displays (620) the user interface in a second state,the second state including visibly displaying one or more of theplurality of alignment guides (e.g., FIG. 5B illustrates that in thesecond state of the user interface, alignment guides are displayed inconjunction with the displayed objects rectangle 502 and diamond 503,i.e., alignment guides 502-a and 502-b with respect to rectangle 502;and alignment guides 503-a, 503-b, and 503-c with respect to diamond503).

In some embodiments, the second state includes displaying a ruler inconjunction with the visibly displayed plurality of alignment guides(622) (e.g., FIG. 5B, in the second state of the user interface, rulers504-1 and 504-2 are displayed).

While moving, resizing, or otherwise adjusting the user interfaceelement within the user interface, and when the velocity of the usergesture exceeds the first predefined velocity threshold, the devicemaintains display of the user interface in the first state (624) (e.g.,FIG. 5D, the user interface is in the first state with respect todisplaying alignment guides because the velocity of user gesture 507-2exceeds the predefined velocity threshold).

In some embodiments, the device initially configures a first alignmentguide in the plurality of alignment guides with a first attractionstrength, and when the velocity of the user gesture exceeds a secondpredefined velocity threshold, the device reconfigures the firstalignment guide with a second attraction strength (626) (e.g., FIG. 5Galignment guide 503-e is set with a first attraction strength of 100%,and user gesture 512-1 exceeds a predefined velocity threshold; FIG. 5H,alignment guide 503-e is reconfigured with a second attraction strengthof 0%).

In alternate embodiments, a first predefined velocity threshold isestablished so that if a user gesture exceeds the threshold, alignmentguides are not visibly displayed; and a distinct second predefinedvelocity threshold is established so that if a user gesture exceeds thethreshold, alignment guides are ignored. In some embodiments, the firstand the second predefined velocity thresholds are the same (628). Insome embodiments, the first and the second predefined velocitythresholds have different values.

In some embodiments, the second attraction strength is zero, and thefirst attraction strength is greater than zero (630) (e.g., FIG. 5Galignment guide 503-e is set with a first attraction strength of 100%,FIG. 5H, alignment guide 503-e is reconfigured with a second attractionstrength of 0%).

In some embodiments, when the velocity of the user gesture exceeds thefirst predefined velocity threshold, the user gesture is moving the userinterface object towards a second user interface object, and the userinterface object and the second user interface object are substantiallyaligned on a common axis, the device selects an alignment guide from theplurality of alignment guides, wherein the selected alignment guide isassociated with the common axis; and the device visibly displays theselected alignment guide in conjunction with the user interface object,the common axis, and the second user interface object (632) (e.g., FIG.5H, alignment guide 503-e is visibly displayed and retains its firstattraction strength of 100%; user gesture 512-1 is moving rectangle 502towards diamond 503, which is on a common axis with rectangle 502;alignment guide 503-e associated with the common axis is visiblydisplayed even though the user gesture velocity exceeded the predefinedvelocity threshold).

In some embodiments, during the user gesture, the device detects aperiod of inactivity that exceeds a predefined duration (e.g., the userquits moving the finger making the gesture for some period of time, suchas 0.2 seconds, but the user has not lifted the finger making thegesture; predefined durations may be any suitable value, including butnot limited to, 0.15 seconds, 0.2 seconds, 0.3 seconds, 0.4 seconds, 0.5seconds, 1 second, etc.); after the period of inactivity, the devicechanges the state of the user interface (e.g., if the user interface wasin the first state with respect to displaying alignment guides, changingto the second state, or vice versa.) (634) (e.g., FIG. 5I, single fingercontact 510 remained in substantially the same location for 0.2 seconds;FIG. 5J, after the period of user gesture inactivity depicted in UI500I, the state of the user interface is changed by visibly displayingalignment guides 502-f, 503-d, and 503-f, and reconfiguring theirattraction strengths to be 100%).

In some embodiments, changing the state of the user interface afterdetecting a period of inactivity includes the device displaying orredisplaying at least some of the plurality of alignment guides,regardless of what state the user interface is currently in.

FIG. 6C is a flow diagram illustrating a method 650 of manipulating userinterface objects with velocity sensitive alignment guides in accordancewith some embodiments. The method 650 is performed at a computing device(e.g., device 300, FIG. 3, or portable multifunction device 100, FIG. 1)with a display and a touch-sensitive surface. In some embodiments, thedisplay is a touch screen display and the touch-sensitive surface is onthe display. In some embodiments, the display is separate from thetouch-sensitive surface.

Some operations in method 650 may be combined and/or the order of someoperations may be changed. Additionally, operations in method 650 may becombined with some operations in method 600 and/or the order of somecombined operations may be changed.

As described below, the method 650 provides an intuitive way tomanipulate user interface objects. The method reduces the cognitiveburden on a user when manipulating user interface objects, therebycreating a more efficient human-machine interface. For battery-operatedcomputing devices, enabling a user to manipulate user interface objectsfaster and more efficiently conserves power and increases the timebetween battery charges.

The method 650 is performed at a computing device with a display and oneor more user input devices adapted to detect user gestures, where thedevice displays a user interface including at least a user interfaceelement configured to be moved resized, or otherwise adjusted within theuser interface in response to user gestures, and a plurality ofalignment guides adapted to indicate potential placement positionswithin the user interface for user interface elements being movedresized, or otherwise adjusted, wherein one or more of the plurality ofalignment guides are configured with a first attraction strength (652)(e.g., FIG. 5A, UI 500A including rectangle 502, and not displayedvisibly in UI 500A, but depicted in FIG. 5B, UI 500B, possible alignmentguides in conjunction with the displayed objects rectangle 502 anddiamond 503, i.e., alignment guides 502-a and 502-b with respect torectangle 502; and alignment guides 503-a, 503-b, and 503-c with respectto diamond 503; see also FIG. 5F, UI 500F including rectangle 502, andnot displayed visibly in UI 500F, but depicted in FIG. 5G, UI 500G,possible alignment guides in conjunction with the displayed objectsrectangle 502 and diamond 503, i.e., alignment guide 502-e with respectto rectangle 502; and alignment guides 503-d, 503-e, and 503-f withrespect to diamond 503).

In some embodiments, the user interface element is displayed on anelectronic canvas (654) (e.g., FIGS. 5A and 5F, the user interfaceincludes an electronic canvas 500, which includes rectangle 502).

In some embodiments, the display and at least one of the one or moreuser input devices comprise a touch-screen display (656) (e.g., FIG. 5A,touch screen 112).

The device detects (658) a user gesture, e.g., a swipe, drag, pinch,depinch, or any suitable user gesture, the user gesture corresponding toa gesture to move resize, or otherwise adjust the user interface elementwithin the user interface (e.g., FIG. 5G, user gesture 512-1).

The device determines a velocity of the user gesture (660) (e.g., FIG.5G, the device determines the velocity of user gesture 512-1, and asdiscussed below, velocity determinations may be implemented by eventsorter 170, event recognizer 180, and event handler 190 by calculatingvelocity from distance and duration data from one or more user gestureevents).

In some embodiments, when the velocity of the user gesture is less thanor equal to the predefined velocity threshold, at least some of theplurality of alignment guides is visibly displayed (662) (e.g., FIG. 5J,the device determines that the velocity of user gesture 512-2 is lessthan a predefined velocity threshold, and in FIG. 5K, alignment guides5024, 503-d, 503-e, and 503-f are visibly displayed).

In some embodiments, when the velocity of the user gesture is greaterthan the predefined velocity threshold, at least some of the pluralityof alignment guides is not visibly displayed (664) (e.g., FIG. 5G, thedevice determines that the velocity of user gesture 512-1 is greaterthan a predefined velocity threshold, and in FIG. 5H, alignment guides502-e, 503-d, and 503-f are not visibly displayed).

In response to detecting the user gesture, the device moves (666) theuser interface element within the user interface in accordance with theuser gesture (e.g., FIG. 5G, user gesture 512-1 to move rectangle 502;FIG. 5H, rectangle 502 has been moved in accordance with gesture 512-1).

While moving the user interface element within the user interface, andwhen the velocity of the user gesture is less than or equal to apredefined velocity threshold, the device maintains the first attractionstrength (668) (e.g., FIG. 5J, the velocity of user gesture 512-2 isless than a predefined velocity threshold, and in FIG. 5K, the devicemaintained the attraction strengths of alignment guides 502-f, 503-d,503-e, and 503-f at 100%).

While moving the user interface element within the user interface, andwhen the velocity of the user gesture exceeds the predefined velocitythreshold, the device configures one or more of the plurality ofalignment guides with a second attraction strength (670) (e.g., FIG. 5G,the velocity of user gesture 512-1 is greater than a predefined velocitythreshold, and in FIG. 5H, the device configured the alignment guides502-e, 503-d, and 503-f with second attraction strengths of 0%).

In some embodiments, the second attraction strength is zero (672) (e.g.,FIG. 5H, the second attraction strengths of alignment guides 502-e,503-d, and 503-f are 0%).

In some embodiments, the device snaps the user interface element to atarget alignment guide when the user interface element is closer than apredefined distance to the target alignment guide, which is configuredwith the first attraction strength (674) (e.g., FIG. 5K, rectangle 502is closer to alignment guide 502-f than predefined distance 509-d;alignment guide 502-f is configured with the first attraction strength,100%; FIG. 5L, rectangle 502 is snapped to alignment guide 502-f).

In some embodiments, the device continues to move the user interfaceelement in accordance with the user gesture when the user interfaceelement is closer than a predefined distance to a target alignmentguide, which is configured with the second attraction strength (676)(e.g., FIG. 5G, user gesture 512-1 moving rectangle 502; FIG. 5H,rectangle 502 has been moved along alignment guide 503-e in accordancewith user gesture 512-1, and has passed directly through alignment guide502-e, which is set with the second attraction strength of zero).

The steps in the information processing methods described above may beimplemented by running one or more functional modules in informationprocessing apparatus such as general purpose processors or applicationspecific chips, such as ASICs, FPGAs, PLDs, or other appropriatedevices. These modules, combinations of these modules, and/or theircombination with general hardware (e.g., as described above with respectto FIGS. 1A, 1B and 3) are all included within the scope of protectionof the invention.

The operations described above with reference to FIGS. 6A-6C may beimplemented by components depicted in FIGS. 1A-1C. For example, usergesture velocity determinations may be implemented by event sorter 170,event recognizer 180, and event handler 190 by calculating velocity fromdistance and duration data from one or more user gesture events. Eventmonitor 171 in event sorter 170 detects a contact on touch-sensitivedisplay 112, and event dispatcher module 174 delivers the eventinformation to application 136-1. A respective event recognizer 180 ofapplication 136-1 compares the event information to respective eventdefinitions 186, and determines whether a first contact at a firstlocation on the touch-sensitive surface corresponds to a predefinedevent or sub-event, such as selection of an object on a user interface.When a respective predefined event or sub-event is detected, eventrecognizer 180 activates an event handler 180 associated with thedetection of the event or sub-event. Event handler 180 may utilize orcall data updater 176 or object updater 177 to update the applicationinternal state 192. In some embodiments, event handler 180 accesses arespective GUI updater 178 to update what is displayed by theapplication. Similarly, it would be clear to a person having ordinaryskill in the art how other processes can be implemented based on thecomponents depicted in FIGS. 1A-1C.

The foregoing description, for purpose of explanation, has beendescribed with reference to specific embodiments. However, theillustrative discussions above are not intended to be exhaustive or tolimit the invention to the precise forms disclosed. Many modificationsand variations are possible in view of the above teachings. Theembodiments were chosen and described in order to best explain theprinciples of the invention and its practical applications, to therebyenable others skilled in the art to best utilize the invention andvarious embodiments with various modifications as are suited to theparticular use contemplated.

What is claimed is:
 1. A method, comprising: at a computing device witha display and one or more user input devices adapted to detect usergestures: displaying a user interface in a first state, the userinterface including at least: a user interface element configured to bemoved within the user interface in response to user gestures, and aplurality of alignment guides adapted to indicate potential placementpositions within the user interface for user interface elements beingmoved; detecting a user gesture, the user gesture corresponding to agesture to move the user interface element within the user interface;determining a velocity of the user gesture; in response to detecting theuser gesture, moving the user interface element within the userinterface in accordance with the user gesture; while moving the userinterface element within the user interface: when the velocity of theuser gesture is less than a first predefined velocity threshold,displaying the user interface in a second state, the second stateincluding visibly displaying one or more of the plurality of alignmentguides; and when the velocity of the user gesture exceeds the firstpredefined velocity threshold, when the user interface object and asecond user interface object are aligned on a directly vertical commonaxis or a directly horizontal common axis, and when the user gesture ismoving the user interface object towards the second user interfaceobject along the directly vertical common axis or the directlyhorizontal common axis: selecting an alignment guide from the pluralityof alignment guides, the selected alignment guide being associated withthe directly vertical common axis or the directly horizontal commonaxis; and visibly displaying the selected alignment guide in conjunctionwith the user interface object, the directly vertical common axis or thedirectly horizontal common axis, and the second user interface object;otherwise: when the velocity of the user gesture does not exceed thefirst predefined velocity threshold, when the user interface object andthe second user interface object are not aligned on the directlyvertical common axis or the directly horizontal common axis, and whenthe user gesture is not moving the user interface object towards thesecond user interface object along the directly vertical common axis orthe directly horizontal common axis: the selected alignment guide andthe directly vertical common axis or the directly horizontal common axisare not displayed.
 2. The method of claim 1, wherein displaying the userinterface in the first state comprises not displaying the plurality ofalignment guides visibly.
 3. The method of claim 1, wherein a firstalignment guide in the plurality of alignment guides is configured witha first attraction strength, and further comprising: when the velocityof the user gesture exceeds a second predefined velocity threshold,reconfiguring the first alignment guide with a second attractionstrength.
 4. The method of claim 3, wherein the first and the secondpredefined velocity thresholds are the same.
 5. The method of claim 3,wherein the second attraction strength is less than the first attractionstrength, and wherein the first attraction strength is greater than alowest attraction strength.
 6. The method of claim 1, wherein theplurality of alignment guides includes one or more alignment guide typesselected from the group consisting of edge-to-middle-slide alignmentguides, edge-to-edge alignment guides, and middle-to-middle alignmentguides.
 7. The method of claim 1, wherein at least some of the pluralityof alignment guides are displayed in conjunction with the user interfaceelement.
 8. The method of claim 1, wherein the second state includesdisplaying a ruler in conjunction with the visibly displayed pluralityof alignment guides.
 9. The method of claim 1, further comprising:during the user gesture: detecting a period of inactivity that exceeds apredefined duration; and after the period of inactivity, changing thestate of the user interface.
 10. The method of claim 1, wherein the userinterface element is displayed on an electronic canvas.
 11. The methodof claim 1, wherein the display and at least one of the one or more userinput devices comprise a touch-screen display.
 12. A computing device,comprising: a display; one or more user input devices adapted to detectuser gestures; one or more processors; memory; and one or more programs,the one or more programs being stored in the memory and configured to beexecuted by the one or more processors, the one or more programsincluding instructions for: displaying a user interface in a firststate, the user interface including at least: a user interface elementconfigured to be moved within the user interface in response to usergestures, and a plurality of alignment guides adapted to indicatepotential placement positions within the user interface for userinterface elements being moved; detecting a user gesture, the usergesture corresponding to a gesture to move the user interface elementwithin the user interface; determining a velocity of the user gesture;in response to detecting the user gesture, moving the user interfaceelement within the user interface in accordance with the user gesture;while moving the user interface element within the user interface: whenthe velocity of the user gesture is less than a first predefinedvelocity threshold, displaying the user interface in a second state, thesecond state including visibly displaying one or more of the pluralityof alignment guides; and when the velocity of the user gesture exceedsthe first predefined velocity threshold, when the user interface objectand a second user interface object are aligned on a directly verticalcommon axis or a directly horizontal common axis, and when the usergesture is moving the user interface object towards the second userinterface object along the directly vertical common axis or the directlyhorizontal common axis: selecting an alignment guide from the pluralityof alignment guides, the selected alignment guide being associated withthe directly vertical common axis or the directly horizontal commonaxis; and visibly displaying the selected alignment guide in conjunctionwith the user interface object, the directly vertical common axis or thedirectly horizontal common axis, and the second user interface object;otherwise: when the velocity of the user gesture does not exceed thefirst predefined velocity threshold, when the user interface object andthe second user interface object are not aligned on the directlyvertical common axis or the directly horizontal common axis, and whenthe user gesture is not moving the user interface object towards thesecond user interface object along the directly vertical common axis orthe directly horizontal common axis: the selected alignment guide andthe directly vertical common axis or the directly horizontal common axisare not displayed.
 13. A computer readable storage medium storing one ormore programs, the one or more programs comprising instructions, which,when executed by a computing device with a display and one or more userinput devices adapted to detect user gestures, cause the device to:display a user interface in a first state, the user interface includingat least: a user interface element configured to be moved within theuser interface in response to user gestures, and a plurality ofalignment guides adapted to indicate potential placement positionswithin the user interface for user interface elements being moved;detect a user gesture, the user gesture corresponding to a gesture tomove the user interface element within the user interface; determine avelocity of the user gesture; in response to detecting the user gesture,move the user interface element within the user interface in accordancewith the user gesture; while moving the user interface element withinthe user interface: when the velocity of the user gesture is less than afirst predefined velocity threshold, displaying the user interface in asecond state, the second state including visibly displaying one or moreof the plurality of alignment guides; and when the velocity of the usergesture exceeds the first predefined velocity threshold, when the userinterface object and a second user interface object are aligned on adirectly vertical common axis or a directly horizontal common axis, andwhen the user gesture is moving the user interface object towards thesecond user interface object along the directly vertical common axis orthe directly horizontal common axis: selecting an alignment guide fromthe plurality of alignment guides, the selected alignment guide beingassociated with the directly vertical common axis or the directlyhorizontal common axis; and visibly displaying the selected alignmentguide in conjunction with the user interface object, the directlyvertical common axis or the directly horizontal common axis, and thesecond user interface object; otherwise: when the velocity of the usergesture does not exceed the first predefined velocity threshold, whenthe user interface object and the second user interface object are notaligned on the directly vertical common axis or the directly horizontalcommon axis, and when the user gesture is not moving the user interfaceobject towards the second user interface object along the directlyvertical common axis or the directly horizontal common axis: theselected alignment guide and the directly vertical common axis or thedirectly horizontal common axis are not displayed.